Information exchange for initial user equipment access

ABSTRACT

A method in a network node including a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node for determining admission of a user equipment (UE) includes the steps: the gNB-DU receiving a connection request from a UE; in response to a determination that the gNB-DU is not able to serve the UE, sending an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) from the gNB-DU to the gNB-CU; in response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, responding to the gNB-DU with a radio resource control (RRC) ConnectionReject message; and transmitting the RRC ConnectionReject message from the gNB-DU to the UE to reject the UE.

PRIORITY

This nonprovisional application is a U.S. National Stage Filing under 35 U.S.C. § 371 of International Patent Application Serial No. PCT/IB2018/059061 filed Nov. 16, 2018 and entitled “INFORMATION EXCHANGE FOR INITIAL USER EQUIPMENT ACCESS” which claims priority to U.S. Provisional Patent Application No. 62/587652 filed Nov. 17, 2017 both of which are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, to admission to a wireless network.

BACKGROUND

The current 5G radio access network (RAN) architecture is shown in TS38.401v0.4.1 (available at this link http://www.3gpp.org/ftp//Specs/archive/38_series/38.401/38401-041.zip) and in FIG. 10. The NG architecture can be further described as follows:

-   -   The NG radio access network (NG-RAN) consists of a set of base         stations (e.g. gNBs) connected to the 5G core network (5GC)         through the NG, an interface between a gNB and the 5G core         network (5GC).     -   An gNB can support frequency division duplex (FDD) mode, time         division duplex (TDD) mode, or dual mode operation.     -   gNBs can be interconnected through the Xn, an interface between         gNBs.     -   A gNB may consist of a gNB central unit (gNB-CU) and one or more         gNB distributed units (gNB-DU). A gNB-CU and a gNB-DU is         connected via an F1 logical interface.     -   In some implementations, one gNB-DU is connected to only one         gNB-CU. For resiliency, a gNB-DU may be connected to multiple         gNB-CU by appropriate implementation.

NG, Xn, and F1 are logical interfaces. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is part of the RNL. For each NG-RAN interface (e.g., NG, Xn, F1), the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signaling transport. In NG-Flex configuration, each gNB is connected to all 5GC nodes within a pool area. The pool area is described in 3GPP TS 23.501. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP (e.g., as described in 3GPP TS 33.401) may be applied.

In the context of RAN 5G architectures, dual connectivity may be supported. Such a mechanism consists of establishing master and secondary nodes and it consists of distributing user plane (UP) traffic to the master node (MN) and secondary nodes (SNs) according to the best possible traffic and radio resource management. Control plane (CP) traffic is assumed to terminate in one node only, (e.g., the MN). FIGS. 11 and 12 show the protocol and interfaces involved in dual connectivity (e.g., as described in TS38.300v0.6.0 available at http://ftp.3gpp.org//Specs/archive/38_series/38.300/38300-060.zip).

FIG. 11 shows that the Master gNB (MgNB) is able to forward packet data convergence protocol (PDCP) bearer traffic to a Secondary gNB (SgNB), while FIG. 12 shows the case where the SGNB forwards PDCP bearer traffic to the MgNB. The MgNB and SgNB may be subject to the RAN split architecture outlined above and made of CUs and DUs.

Furthermore, in the context of 5G standardization, multi-RAT dual connectivity (MR-DC) is being specified. When MR-DC is applied, a RAN node (the master node, MN) anchors the control plane towards the CN (e.g. a control node or a child node), while another RAN node (the secondary node, SN) provides control and user plane resources to the UE via coordination with the MN, as shown in FIG. 13.

Within the scope of MR-DC, various user plane/bearer type solutions are possible, as seen in FIG. 14.

In TS 38.401, overall procedures are depicted, including signaling flows in gNB-CU/gNB-DU architecture (e.g. initial access from the UE, inter-DU mobility etc.).

There currently exist certain challenge(s). In the split RAN (gNB-CU/gNB-DU) architecture, in the initial user equipment (UE) access procedure, it can occur that there is a resource shortage in the gNB-DU. In this case, the initial UE access procedure may fail due to a rejection from the gNB-DU. The gNB-DU performs admission control of the UE at reception of Msg3 (e.g., when the gNB-DU decides whether to allocate the first set of resources to the UE for lower layer signaling (measurement reports, SIB1 signaling)). If the outcome of the initial admission at the gNB-DU is not known in time at the gNB-CU, it will result in unnecessary signaling and the gNB-CU not being able to know if an RRCConnectionReject needs to be triggered. A way to handle this failure case has not been defined.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. In this disclosure, a mechanism that allows the gNB-DU to notify the gNB-CU about the outcome of the UE admission at the gNB-DU is outlined. This allows the gNB-CU to decide on the next steps, resulting in improved performance as it provides the means to know in time and handle the case that the UE request is rejected. The proposed information exchange can cater for various cases based on the outcome of the UE admission at the gNB-DU. They are represented by the following embodiments:

-   -   Embodiment 1: The gNB-DU does not allocate resources to the UE         (e.g., the UE is allowed to signal Msg3 via signaling radio         bearer 1 (SRB1), but it is not admitted to further resources in         the gNB-DU). This information implies an RRCConnectionRejection         will be sent from the gNB-CU.     -   Embodiment 2: The gNB-DU is able to admit the UE (e.g., allocate         resources for lower layer signaling), but the gNB-DU is         experiencing a high load situation. The gNB-CU can therefore         judge from the RRC access cause whether to admit the UE (e.g. if         the UE is connecting for an emergency call) or whether to reject         the UE.     -   Embodiment 3: The gNB-DU admits the UE without any particular         event to be signaled to the gNB-CU. In this case the gNB-DU can         simply state to the gNB-CU that the UE was admitted.     -   Embodiment 4: The gNB-DU does not allocate resources to the UE.         The gNB-DU implicitly informs the gNB-CU that the UE has not         been admitted by sending an Initial UL RRC message that does not         include a configuration for SRB1. In response to receiving the         Initial UL RRC message, the gNB-CU sends a RRCConnectionReject         message to the gNB-DU and the UE.     -   Embodiment 5: The gNB-DU does not allocate resources to the UE.         The gNB-DU sends to the gNB-CU an Initial UL RRC message that         includes the admission result that indicates the cause of the         admission result. In response, the gNB-CU sends an         RRCConnectionReject message to the gNB-DU and the UE.

This disclosure contemplates a method that allows the gNB-DU to notify the gNB-CU about the outcome of the UE admission at the gNB-DU at reception of Msg3 and a method that allows the gNB-CU to decide on the next steps in the UE initial access based on the outcome of the UE admission.

According to an embodiment, a method in a network node including a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node for determining admission of a user equipment (UE) includes the steps: the gNB-DU receiving a connection request from a UE; in response to a determination that the gNB-DU is not able to serve the UE, sending an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) from the gNB-DU to the gNB-CU; in response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, responding to the gNB-DU with a radio resource control (RRC) ConnectionReject message; and transmitting the RRC ConnectionReject message from the gNB-DU to the UE to reject the UE.

According to another embodiment, a network node for determining admission of a user equipment (UE) includes a memory and processing circuitry communicatively coupled to the memory. The memory and the processing circuitry are configured to implement a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node. The gNB-DU receives a connection request from a UE and in response to a determination that the gNB-DU is not able to serve the UE, send an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) from the gNB-DU to the gNB-CU. The gNB-CU, in response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, responds to the gNB-DU with a radio resource control (RRC) ConnectionReject message. The gNB-DU transmits the RRC ConnectionReject message from the gNB-DU to the UE to reject the UE.

According to yet another embodiment, a user equipment (UE) includes a memory and processing circuitry coupled to the memory. The memory and the processing circuitry send a connection request to a network node. The network node includes a memory and processing circuitry that implement a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node. In response to a determination that the gNB-DU is not able to serve the UE, the gNB-DU sends an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) to the gNB-CU. In response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, the gNB-CU responds to the gNB-DU with a radio resource control (RRC) ConnectionReject message. The gNB-DU transmits the RRC ConnectionReject message from the gNB-DU to the UE.

According to an embodiment, a method in a network node including a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node for determining admission of a user equipment (UE) includes the steps: the gNB-DU receiving a connection request from a UE; in response to a determination that the gNB-DU is not able to serve the UE, sending an initial uplink radio resource control (UL RRC) message that indicates that the connection request should be rejected, the UL RRC message comprising a cause value that indicates a reason why the connection request should be rejected from the gNB-DU to the gNB-CU; in response to receiving, at the gNB-CU, the UL RRC message, responding to the gNB-DU with a radio resource control (RRC) ConnectionReject message; and transmitting the RRC ConnectionReject message from the gNB-DU to the UE to reject the UE.

There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. In one embodiment, a method is performed by a base station for admitting a user equipment. The method includes receiving from the user equipment at a distributed unit of the base station a connection request, determining whether the distributed unit is able to admit the user equipment, and communicating from the distributed unit to a central unit of the base station a message indicating whether the user equipment is able to admit the user equipment. The message may indicate one or more of (1) whether the distributed unit is able to allocate resources to the user equipment and (2) whether the UE is under high load. The distributed unit may also receive a response from the central unit indicating whether to admit or reject the user equipment.

Certain embodiments may provide one or more of the following technical advantage(s). For example, an embodiment allows the gNB-DU to inform the gNB-CU of the outcome of the UE admission at the gNB-DU. In that way a streamlined way to handle failures at the initial UE access procedure is provided. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 is an illustration of an exemplary wireless network, in accordance with certain embodiments;

FIG. 2 is an illustration of an exemplary user equipment, in accordance with certain embodiments;

FIG. 3 is an illustration of an exemplary virtualization environment, in accordance with certain embodiments;

FIG. 4 is an illustration of an exemplary telecommunication network connected via an intermediate network to a host computer, in accordance with certain embodiments;

FIG. 5 is an illustration of an exemplary host computer communicating via a base station with a user equipment over a partially wireless connection, in accordance with certain embodiments;

FIGS. 6-9 are flowcharts showing exemplary methods implemented in a communication system including a host computer, a base station and a user equipment, in accordance with certain embodiments;

FIG. 10 is an illustration of an exemplary network architecture, in accordance with certain embodiments;

FIG. 11 is an illustration of exemplary network nodes, in accordance with certain embodiments;

FIG. 12 is an illustration of exemplary network nodes, in accordance with certain embodiments;

FIG. 13 is an illustration of an exemplary network nodes, in accordance with certain embodiments;

FIG. 14 is an illustration of exemplary network nodes, in accordance with certain embodiments;

FIGS. 15-20 are flowcharts showing exemplary methods implemented in a communication system, in accordance with certain embodiments;

FIG. 21 is a flowchart showing an exemplary method, in accordance with certain embodiments;

FIG. 22 is an illustration of an exemplary virtualization apparatus, in accordance with certain embodiments.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

In existing telecommunications networks, a user equipment (UE) gains admission to the network by sending a request to the network seeking admission. A network node (e.g., eNodeB) determines whether the UE should be granted admission (e.g., whether there are sufficient network resources to handle the UE) and then sends a message to the UE indicating whether admission has been granted or rejected.

In a 5G network, the network node (e.g., a gNB) may have different logical nodes that perform different functions (e.g., a split RAN architecture). One logical node (e.g., a gNB-Distributed Unit (DU)) may determine whether the UE should be granted access. Another logical node (e.g., a gNB-Central Unit (CU)) may send a message to the UE indicating whether admission has been granted. In some instances, there does not exist an agreed upon way for the gNB-DU to signal to the gNB-CU that admission has been denied. As a result, the gNB-CU may not send a message to the UE indicating that admission has been rejected.

This disclosure contemplates a process that allows the gNB-DU to signal to the gNB-CU that a UE has not been granted admission to the network. In one embodiment, the gNB-DU sends the gNB-CU an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1). In response to receiving this message, the gNB-CU sends a radio resource control (RRC) ConnectionReject message to the gNB-DU. The gNB-DU then sends the RRC ConnectionReject message to the UE.

In an alternative embodiment, the gNB-DU sends the gNB-CU an UL RRC message that indicates that the connection request should be rejected and that includes a cause value that indicates a reason why the connection request should be rejected. In response to receiving this message, the gNB-CU sends a radio resource control (RRC) ConnectionReject message to the gNB-DU. The gNB-DU then sends the RRC ConnectionReject message to the UE. These and other embodiments will be described in more detail using FIGS. 1-22.

FIG. 1 is an illustration of an exemplary wireless network, in accordance with certain embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 1. For simplicity, the wireless network of FIG. 1 only depicts network 106, network nodes 160 and 160 b, and WDs 110, 110 b, and 110 c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and WD 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIG. 1, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIG. 1 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality. For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIG. 1 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114. Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be considered to be integrated.

User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110, and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.

FIG. 2 is an illustration of an exemplary user equipment, in accordance with certain embodiments. FIG. 2 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIG. 2, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIG. 2 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIG. 2, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIG. 2, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIG. 2, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIG. 2, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243 a. Network 243 a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243 a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.

In FIG. 2, processing circuitry 201 may be configured to communicate with network 243 b using communication subsystem 231. Network 243 a and network 243 b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243 b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243 b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243 b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG. 3 is an illustration of an exemplary virtualization environment, in accordance with certain embodiments. FIG. 3 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIG. 3, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in FIG. 3.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

FIG. 4 is an illustration of an exemplary telecommunication network connected via an intermediate network to a host computer, in accordance with certain embodiments. With reference to FIG. 4, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412 a, 412 b, 412 c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413 a, 413 b, 413 c. Each base station 412 a, 412 b, 412 c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413 c is configured to wirelessly connect to, or be paged by, the corresponding base station 412 c. A second UE 492 in coverage area 413 a is wirelessly connectable to the corresponding base station 412 a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIG. 4 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIG. 5 is an illustration of an exemplary host computer communicating via a base station with a user equipment over a partially wireless connection, in accordance with certain embodiments. Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 5. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIG. 5) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIG. 5) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIG. 5 may be similar or identical to host computer 430, one of base stations 412 a, 412 b, 412 c and one of UEs 491, 492 of FIG. 4, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 5 and independently, the surrounding network topology may be that of FIG. 4.

In FIG. 5, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the response time of the network, specifically a NG-RAN, by allowing a gNB-DU to inform a gNB-CU about the outcome of a UE admission and thereby provide benefits such as reduced user waiting time and improved network responsiveness.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIG. 6 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 4 and 5. For simplicity of the present disclosure, only drawing references to FIG. 6 will be included in this section. In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG. 7 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 4 and 5. For simplicity of the present disclosure, only drawing references to FIG. 7 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

FIG. 8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 4 and 5. For simplicity of the present disclosure, only drawing references to FIG. 8 will be included in this section. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG. 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 4 and 5. For simplicity of the present disclosure, only drawing references to FIG. 9 will be included in this section. In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIGS. 15-20 are flowcharts showing exemplary methods implemented in a communication system, in accordance with certain embodiments. In FIG. 15, the initial UE access procedure up to RRC Connection Setup is presented. It is shown that the initial UE admission is done in the gNB-DU at reception of Msg3 and that RRC message transfer procedures between gNB-DU and gNB-CU are used after reception of Msg3.

In some implementations, some level of resource allocation can be carried out at the gNB-DU at the time MSg3 is received. This resource allocation may involve allocation of resources for channel quality information (CQI) or sounding reference signal (SRS) reporting. Resources needed for UE communication over SRB1 should be reserved. The resources that the UE needs to be admitted may reside purely in the gNB-DU and may not need to be informed to the gNB-CU.

So, when the UE is admitted to communicate via SRB1, a pre-UE-context is created at the gNB-DU and F1 application protocol (F1AP) identifiers (IDs) are stored at the gNB-CU. The F1AP IDs will be used to transfer RRC messages over the F1 control plane (F1-C). Various embodiments depicting the different cases that can occur are discussed below.

Embodiment 1

In this embodiment, the gNB-DU does not allocate resources to the UE. The UE is allowed to signal Msg3 via SRB1, but it is not admitted to further resources in the gNB-DU.

As shown in FIG. 16, the gNB-DU receives Msg3 (RRCConnectionRequest) in step 1620 and it runs a first admission control for lower layer resource allocation in the gNB-DU. Subsequently in step 1625, the gNB-DU sends the F1AP: INITIAL UL RRC MESSAGE to the gNB-CU including the results of the gNB-DU admission. Based on this gNB-DU admission information, the gNB-CU sends an RRCConnectionRejection to the gNB-DU in step 1630.

Embodiment 2

In this embodiment, the gNB-DU is able to admit the UE (e.g., allocate resources for lower layer signaling), but the gNB-DU is under high load.

As shown in FIG. 17, the gNB-DU receives Msg3 (RRCConnectionRequest) in step 1720 and again it runs a first admission control for lower layer resource allocation in the gNB-DU. Subsequently in step 1725, the gNB-DU sends the F1AP: INITIAL UL RRC MESSAGE to the gNB-CU including the results of the gNB-DU admission. The gNB-CU gets the gNB-DU admission information in step 1730 and based on the RRC access cause, it can judge whether to admit the UE (e.g. if the UE is connecting for an emergency call) or whether to reject the UE.

Embodiment 3

In this embodiment, the gNB-DU has admitted the UE without any particular event to be signaled to the gNB-CU.

As shown in FIG. 18, the gNB-DU receives Msg3 (RRCConnectionRequest) in step 1820 and as in the other embodiments, it runs a first admission control for lower layer resource allocation in the gNB-DU. Subsequently in step 1825, the gNB-DU sends the F1AP: INITIAL UL RRC MESSAGE to the gNB-CU including the results of the gNB-DU admission. In this case, the gNB-DU can simply state to the gNB-CU that the UE was admitted. Based on this information the gNB-CU sends an RRC Connection Setup to the UE via the gNB-DU in steps 1830 and 1835.

Embodiment 4

In another embodiment, shown in FIG. 19, the newly added information about gNB-DU UE admission results may be used not only at UE initial access but also at other stages of the UE connection lifespan. As an example, the gNB-DU may, at any point in time of serving the UE, find itself in a situation where the low layer resources needed to serve the UE are not available anymore. In this case, either

-   -   the information element (IE) suggested below, which is named as         an example “gNB-DU Admission Result”, can be populated with new         cause values such as:     -   “Resources not available”, indicating that there are no more         resources to serve the UE and that the CU shall remove the UE         connection, for example with an RRC Release.     -   “High Load”, indicating that low layer resources are very scarce         and that the CU should evaluate whether to keep the UE connected         (e.g., because the UE is on a high priority service such as an         emergency call) or to remove the U connection (e.g., with an RRC         Release).     -   The IE suggested below, which is named as an example “gNB-DU         Admission Result”, can be reused as defined below. In this case:     -   Value “Rejected” should be interpreted as indicating that there         are no more resources to serve the UE and that the CU shall         remove the UE connection, for example with an RRC Release.     -   Value “Admitted High Load” should be interpreted as indicating         that low layer resources are very scarce and that the CU should         evaluate whether to keep the UE connected (e.g., because the UE         is on a high priority service such as an emergency call) or to         remove the user plane connection (for example with an RRC         Release).     -   Introduce a new IE for example named gNB-DU resource status,         which might have values such as:     -   “Resources not available”, indicating that there are no more         resources to serve the UE and that the CU shall remove the UE         connection (e.g., with an RRC Release).     -   “High Load”, indicating that low layer resources are very scarce         and that the CU should evaluate whether to keep the UE connected         (e.g., because the UE is on a high priority service such as an         emergency call) or to remove the U connection (e.g., with an RRC         Release).

This indication may be signaled from gNB-DU to gNB-CU via the F1-C interface and for example, using the UE Context Modification Required procedure.

In another variant of this solution, shown in FIG. 20, the gNB-DU can implicitly inform the gNB-CU that the UE has not been admitted. For example, the gNB-DU can send an Initial UL RRC messages that does not include a configuration for SRB1 in step 2025. Alternatively, the gNB-DU can send an Initial UL RRC messages that does not include a Cell Radio Network Temporary Identity (C-RTNI) for the UE. The CU can then implicitly understand that the gNB-DU has not admitted the UE as shown by the response in 2030.

Proposed Enhancements in the Initial UL RRC Message

To facilitate the above analyzed mechanism, an IE is added to the Initial UL RRC Message, the gNB-DU Admission Result IE. The following cases can be observed:

-   -   If the gNB-DU Admission Result IE is included in the INITIAL UL         RRC MESSAGE TRANSFER, and if the IE is set to “Admitted”, the         gNB-CU may assume that the gNB-DU did not detect any issues with         serving such UE.     -   If the gNB-DU Admission Result IE is included in the INITIAL UL         RRC MESSAGE TRANSFER, and if the IE is set to “Rejected”, the         gNB-CU may reject the UE under the assumption that the gNB-DU is         not able to serve such UE.     -   If the gNB-DU Admission Result IE is included in the INITIAL UL         RRC MESSAGE TRANSFER, and if the IE is set to “Admitted High         Load”, the gNB-CU may admit the UE if it has sufficient         priority.

The Initial UL RRC Message Transfer would then be

Initial UL RRC Message Transfer IE type and Assigned IE/Group Name Presence Range reference Semantics description Criticality Criticality Message Type M 9.3.1.1 YES ignore gNB-DU UE F1AP ID M 9.3.1.5 YES reject PCI (FFS) M FFS Physical Cell Identifier FFS- FFS of the serving cell C-RNTI M FFS C-RNTI allocated at the YES reject gNB-DU RRC-Container M 9.3.1.6 gNB-DU Admission Result M 9.3.1.x YES reject

where

gNB-DU Admission Result IE IE/Group Name Presence Range IE type and reference Semantics description gNB-DU Admission M ENUMERATED (Admitted, Description of UE admission Result Rejected, Admitted High results after signaling of Load, . . .) RRCConnectionRequest

FIG. 21 is a flowchart showing an exemplary method, in accordance with certain embodiments. The method begins at step 2102 with a gNB-DU receiving an RRC Connection Request message from a UE. The gNB-DU then communicates to a gNB-CU an RRC message indicating a result of UE admission at the gNB-DU in step 2104. In step 2106, the gNB-DU receives from the gNB-CU at the gNB-DU an RRC message transfer based on the UE admission result.

FIG. 22 illustrates a schematic block diagram of an apparatus 2200 in a wireless network (for example, the wireless network shown in FIG. 1). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIG. 1). Apparatus 2200 is operable to carry out the example method described with reference to FIG. 21 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIG. 21 is not necessarily carried out solely by apparatus 2200. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2200 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause Receiving Unit 2202, and Communicating Unit 2204 and any other suitable units of apparatus 2200 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in FIG. 22, apparatus 2200 includes Receiving Unit 2202 and Communicating Unit 2204. Receiving unit 2202 is configured to receive messages from a UE (e.g., an RRC Connection Request) and/or a gNB-CU (e.g., an RRC message transfer). Communicating Unit 2204 is configured to communicates messages (e.g., an RRC message) to a gNB-CU.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure, as defined by the following claims.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

-   -   1×RTT CDMA2000 1× Radio Transmission Technology     -   3GPP 3rd Generation Partnership Project     -   5G 5th Generation     -   5GC 5G Core Network     -   ABS Almost Blank Subframe     -   AMF Access and Mobility Management Function     -   ARQ Automatic Repeat Request     -   AWGN Additive White Gaussian Noise     -   BCCH Broadcast Control Channel     -   BCH Broadcast Channel     -   CA Carrier Aggregation     -   CC Carrier Component     -   CCCH SDU Common Control Channel SDU     -   CDMA Code Division Multiplexing Access     -   CGI Cell Global Identifier     -   CIR Channel Impulse Response     -   CP Control Plane     -   CPICH Common Pilot Channel     -   CPICH Ec/No CPICH Received energy per chip divided by the power         density in the band     -   CQI Channel Quality information     -   C-RNTI Cell RNTI     -   C-RTNI Cell Radio Network Temporary Identity     -   CSI Channel State Information     -   CU Centralized Unit     -   CU-CP CU Control Plane     -   CU-UP CU User Plane     -   DCCH Dedicated Control Channel     -   DL Downlink     -   DM Demodulation     -   DMRS Demodulation Reference Signal     -   DRX Discontinuous Reception     -   DTX Discontinuous Transmission     -   DTCH Dedicated Traffic Channel     -   DU Distributed Unit     -   DUT Device Under Test     -   E-CID Enhanced Cell-ID (positioning method)     -   E-SMLC Evolved-Serving Mobile Location Centre     -   ECGI Evolved CGI     -   eNB E-UTRAN NodeB     -   ePDCCH enhanced Physical Downlink Control Channel     -   E-SMLC evolved Serving Mobile Location Center     -   E-UTRA Evolved UTRA     -   E-UTRAN Evolved UTRAN     -   F1-C F1 Control Plane     -   FDD Frequency Division Duplex     -   FFS For Further Study     -   GERAN GSM EDGE Radio Access Network     -   gNB Base station in NR     -   gNB-CU gNB Central Unit     -   gNB-DU gNB Distributed Unit     -   GNSS Global Navigation Satellite System     -   GSM Global System for Mobile communication     -   HARQ Hybrid Automatic Repeat Request     -   HO Handover     -   HSPA High Speed Packet Access     -   HRPD High Rate Packet Data     -   LOS Line of Sight     -   LPP LTE Positioning Protocol     -   LTE Long-Term Evolution     -   MAC Medium Access Control     -   MBMS Multimedia Broadcast Multicast Services     -   MBSFN Multimedia Broadcast multicast service Single Frequency         Network     -   MBSFN ABS MBSFN Almost Blank Subframe     -   MCG Master cell group     -   MDT Minimization of Drive Tests     -   MIB Master Information Block     -   MME Mobility Management Entity     -   MSC Mobile Switching Center     -   NDS/IP Network domain security for IP network     -   NG-C NG control plane     -   NPDCCH Narrowband Physical Downlink Control Channel     -   NR New Radio     -   OCNG OFDMA Channel Noise Generator     -   OFDM Orthogonal Frequency Division Multiplexing     -   OFDMA Orthogonal Frequency Division Multiple Access     -   OSS Operations Support System     -   OTDOA Observed Time Difference of Arrival     -   O&M Operation and Maintenance     -   PBCH Physical Broadcast Channel     -   P-CCPCH Primary Common Control Physical Channel     -   PCell Primary Cell     -   PCFICH Physical Control Format Indicator Channel     -   PDCCH Physical Downlink Control Channel     -   PDCP Packet Data Convergence Protocol     -   PDP Profile Delay Profile     -   PDSCH Physical Downlink Shared Channel     -   PGW Packet Gateway     -   PHICH Physical Hybrid-ARQ Indicator Channel     -   PLMN Public Land Mobile Network     -   PMI Precoder Matrix Indicator     -   PRACH Physical Random Access Channel     -   PRS Positioning Reference Signal     -   PSS Primary Synchronization Signal     -   PUCCH Physical Uplink Control Channel     -   PUSCH Physical Uplink Shared Channel     -   RACH Random Access Channel     -   QAM Quadrature Amplitude Modulation     -   RAN Radio Access Network     -   RAT Radio Access Technology     -   RLC Radio Link Control protocol     -   RLM Radio Link Management     -   RNC Radio Network Controller     -   RNL Radio Network Layer     -   RNTI Radio Network Temporary Identifier     -   RRC Radio Resource Control     -   RRM Radio Resource Management     -   RS Reference Signal     -   RSCP Received Signal Code Power     -   RSRP Reference Symbol Received Power OR Reference Signal         Received Power     -   RSRQ Reference Signal Received Quality OR Reference Symbol         Received Quality     -   RSSI Received Signal Strength Indicator     -   RSTD Reference Signal Time Difference     -   SCG Secondary cell group     -   SCH Synchronization Channel     -   SCell Secondary Cell     -   SDAP Service Data Adaptation Protocol     -   SDU Service Data Unit     -   SFN System Frame Number     -   SGW Serving Gateway     -   SI System Information     -   SIB System Information Block     -   SNR Signal to Noise Ratio     -   SON Self Optimized Network     -   SS Synchronization Signal     -   SRB1 Signaling Radio Bearer 1     -   SRS Sounding Reference Signal     -   SSS Secondary Synchronization Signal     -   TDD Time Division Duplex     -   TDOA Time Difference of Arrival     -   TNL Transport Network Layer     -   TOA Time of Arrival     -   TSS Tertiary Synchronization Signal     -   TTI Transmission Time Interval     -   U User/User Plane     -   UE User Equipment     -   UL Uplink     -   UMTS Universal Mobile Telecommunication System     -   UP User Plane     -   USIM Universal Subscriber Identity Module     -   UTDOA Uplink Time Difference of Arrival     -   UTRA Universal Terrestrial Radio Access     -   UTRAN Universal Terrestrial Radio Access Network     -   Uu Radio Interface     -   WCDMA Wide CDMA     -   WLAN Wide Local Area Network     -   Xn-C Xn Control Plane 

The invention claimed is:
 1. A method in a network node comprising a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node for determining admission of a user equipment (UE), the method comprising: the gNB-DU receiving a connection request from a UE; in response to a determination that the gNB-DU is not able to serve the UE, sending an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) from the gNB-DU to the gNB-CU; in response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, responding to the gNB-DU with a radio resource control (RRC) ConnectionReject message; and transmitting the RRC ConnectionReject message from the gNB-DU to the UE to reject the UE.
 2. The method of claim 1, wherein: the gNB-DU makes the determination that the gNB-DU is not able to serve the UE; and the gNB-CU determines that the UL RRC message does not include the configuration for SRB1.
 3. The method of claim 1, wherein the distributed unit allocates no resources to the UE in response to the determination that the gNB-DU is not able to serve the UE.
 4. The method of claim 1, wherein the gNB-DU communicates with the gNB-CU via an F1 logical interface.
 5. A network node for determining admission of a user equipment (UE), the network node comprising: a memory; and processing circuitry communicatively coupled to the memory, the memory and the processing circuitry configured to implement a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node, the gNB-DU configured to: receive a connection request from a UE; and in response to a determination that the gNB-DU is not able to serve the UE, send an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) from the gNB-DU to the gNB-CU; and the gNB-CU configured to, in response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, respond to the gNB-DU with a radio resource control (RRC) ConnectionReject message; the gNB-DU further configured to transmit the RRC ConnectionReject message from the gNB-DU to the UE to reject the UE.
 6. The network node of claim 5, further comprising a second gNB-DU.
 7. The network node of claim 5, wherein the gNB-DU allocates no resources to the UE in response to the determination that the gNB-DU is not able to serve the UE.
 8. The network node of claim 5, wherein the gNB-DU communicates with the gNB-CU via an F1 logical interface.
 9. The network node of claim 5 further configured to communicate with a 5G core network.
 10. A user equipment (UE) comprising: a memory and processing circuitry communicatively coupled to the memory, the memory and the processing circuitry configured to: send a connection request to a network node, the network node comprising a memory and processing circuitry configured to implement a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node, wherein: in response to a determination that the gNB-DU is not able to serve the UE , the gNB-DU sends an initial uplink radio resource control (UL RRC) message that does not include a configuration for signaling radio bearer 1 (SRB1) to the gNB-CU; in response to receiving, at the gNB-CU, the UL RRC message that does not include the configuration for SRB1, the gNB-CU responds to the gNB-DU with a radio resource control (RRC) ConnectionReject message; and the gNB-DU transmits the RRC ConnectionReject message from the gNB-DU to the UE.
 11. The UE of claim 10, wherein the gNB-DU allocates no resources to the UE in response to the determination that the gNB-DU is not able to serve the UE.
 12. The UE of claim 10, wherein the gNB-DU communicates with the gNB-CU via an F1 logical interface.
 13. The UE of claim 10, wherein the network node is further configured to communicate with a 5G core network.
 14. A method in a network node comprising a gNB-Distributed Unit (DU) logical node and a gNB-Central Unit (CU) logical node for determining admission of a user equipment (UE), the method comprising: the gNB-DU receiving a connection request from a UE; the gNB-DU transmitting an initial uplink message to the gNB-CU; the gNB-DU receiving a connection setup from the gNB-CU; the gNB-DU transmitting the connection setup to the UE; determining that the gNB-DU no longer has enough resources to continue the connection with the UE; the gNB-DU sending a request to the gNB-CU to remove the UE connection; the gNB-DU receiving from the gNB-CU a connection release message; and transmitting the connection release message from the gNB-DU to the UE to release the connection.
 15. The method of claim 14, wherein the request to the gNB-CU to remove the UE connection includes a cause value.
 16. The method of claim 15, wherein the cause value indicates that there are insufficient resources to serve the UE.
 17. The method of claim 15, wherein the cause value indicates that there are no resources to serve the UE. 